SDF App
SDF Appis compatible with the existing Java library method (SCSL.jar)Lightweight JAR-based applicationto, It provides document encryption/decryption and security policy processing functions without modifying the code of the business system.
1. Overview
A deployment method suitable for on-premises or VM-based server environments, maintaining the existing SCSL.jar integration structure as is.
| item | Content |
|---|---|
| Deployment Type | JAR-based standalone application |
| Target Environment | On-premises / VM-based server environment |
| Terms of Use | Customers registered with Security365 |
| Compatibility | Maintain the existing SCSL.jar function call method as is. |
2. Components
The main elements included in the SDF App configuration are as follows.
| Components | role |
|---|---|
| Business System | Business application requesting security document processing |
| SDF App (scsl.jar) | Lightweight executable JAR maintaining the same interface as the existing method |
| SDF Container | Process API requests and perform actual encryption tasks |
| EnDec Service | Key Lookup and Security Document Header Generation (Based on SKMS / EKMS) |
| SCI Server | Central Key Server Related to Encryption Key Storage/Retrieval |
| Key Vault (KMS) | Integrating with EnDec as an encryption key management server |
| Log Service | Security Processing History and Log Storage |
| InfoLineage | Document Distribution History and Flow Tracking Data Collection |
3. Integration Flow
The encryption/decryption process based on the SDF App proceeds in the following order.
| step | Processing details |
|---|---|
| 1. SDF App Call | The business system calls the SDF App (scsl.jar) in the same way as the existing function call method. |
| 2. API Request Delivery | SDF App internally calls the SDF Container API to start processing. |
| 3. EnDec Processing | SDF Container performs key retrieval and header generation through the EnDec service. |
| 4. Encryption/Decryption Execution | SDF Container performs file encryption/decryption directly and generates results. |
| 5. Response Return | Send the processing result to the SDF App, and the business system receives the response in the same way as before. |
- Business system iswithout changing the existing function call structureYou can use it as is.
- The SDF App communicates internally with the SDF Container to perform all security processing.
4. Key Features
| Features | Description |
|---|---|
| Minimize code changes | Maintaining the existing SCSL.jar function call method requires no separate development. |
| Flexible Deployment | Can be installed on an internal server of the business system or a separate independent server. |
| Lightweight Configuration | Immediately applicable without separate infrastructure configuration based on JAR. |
| Existing Environment Compatibility | Available in non-containerized environments such as on-premises, VM, etc. |
5. Precautions
- SDF App isCustomers registered with Security365can be used.
- SDF App internallyCommunication with the SDF Container is essentialand the Container must be pre-deployed.
- Detailed deployment guide isSDF App Deployment GuidePlease refer to the document.